Tech Arsenal 1

home *** CD-ROM | disk | FTP | other *** search

/ Tech Arsenal 1 / Tech Arsenal (Arsenal Computer).ISO / tek-20 / bb21c.zip / FWD.DOC < prev next >

Wrap

Text File | 1992-11-19 | 19KB | 500 lines

To forward to a station, that station must now be designated a BBS or a personal BBS. Use the EU command and set the proper flag. B flag -- Old BBS programs that don't have the [xxx] info A flag -- Advanced BBS that does send [xxx]. When in doubt, use this flag P flag -- Personal BBS. Rather than the current way of having a list of destinations for each route, a list of routes for each destination is used. The data has been broken into two pieces. How to connect with a distant mailbox is in the PATH file while the information on what to send is in the ROUTE file. * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * The ROUTE File -------------- A line from the ROUTE file is organized as: W3IWI W0RLI WB6ASR 80 KE6BX This says to send mail for W3IWI mailbox down the path named either W0RLI, WB6ASR, and then KE6BX. The forwarding will be performed in that order. W0RLI will be tried first and then WB6ASR. If a message is more than 80 hours old, KE6BX will be used (See special case: numbers below) Wildcards are supported. For full details on these, see WILDCARD.DOC. Just more than * is supported. Once a message (or a member of a distribution list has been selected, it cannot be selected for another route. 95020 AA4RE 95* W0RLI A message with a route code of 95020 will go to AA4RE. All others go to W0RLI. 95020 will not since it was selected for the AA4RE route already. The ROUTE files also allows ALIASES. These are of the form SOCAL = K6IYK W6PW Anywhere SOCAL appears in a route, K6IYK W6PW will be substituted. So if the ROUTE file says WB6YMH SOCAL this is the same as WB6YMH K6IYK W6PW Aliases only affect the path to use. Aliases must be listed before they can be used. >>> Hierarchial addresses The full hierarchical address is checked. The "#" and "." are not ignored. Search is right to left. Examples: Address #NOCAL.CA.USA.NA Matches NA USA\.NA CA\.USA\.NA "#NOCAL\.CA\.USA\.NA Note the use of the double quote. This is because the "#" is also a wild card character for numbers! The double quote says to interpret the next character literally. The backslash "\" is used for optional material. Thus the pattern USA\.NA matches both USA and USA.NA. >>> Special case: LEAVE If you send something to LEAVE then it will stay on the BBS and not be forwarded. This is handy to prevent just certain messages to stay. Example: 95020 LEAVE 95* KE6BX A message to 95020 will stay but all other 95anything will go to KE6BX. >>> Special case: @BLANK If the special @BLANK is used, this will match any message where the @BBS field is blank. Combining LEAVE and BLANK make some route tables easy: AA4RE LEAVE @BLANK LEAVE * WB6ZVW Any message addressed to @AA4RE stays. Any message addressed to anycall without @ will stay. All others will go to WB6ZVW. This is very handy for a small BBS where everything but local calls go to one other BBS. >>> Special case: ? If you send something to ? then it will stay on the BBS and not be forwarded. It will show up if you execute the L? command. Example: USA ? A message to USA will be marked with the ? flag >>> Special case: numbers The numbers in a route file pertain to time delay Example: W3IWI W0RLI 20 WB6ASR +5 WB6ZVW 80 KE6BX This means send traffic to W0RLI to W3IWI anytime. If a message if more than 20 hours old then also try to forward it to WB6ASR. If a message is 25 hours old (20 from before WB6ASR +5) to WB6ZVW and after 80 hours to KE6BX. The use of the "+5" should be confined to ALIAS statements since it requires more computation. I would use something like: OTHER = WB6ASR +5 WB6ZVW +10 KE6BX W3IWI KA6FUB 10 OTHER This would be interpreted as W3IWI 10 WB6ASR 15 WB6ZVW 20 KE6BX >>> Special case: DONE If you send something to DONE then it will sbe marked as already forwarded. This is handy marking message done for dead systems or for giving up on forwarding bulletins after a certain length of time. Example: ALLUS AA4RE 6 DONE A message to USA will be forwarded to AA4RE. After trying for 6 hours, the message will be marked as forwarded. * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * The PATH File ------------- The PATH file has the entries that describe how to connect to a mailbox we want to forward to. A typical entry: PATH W0RLI B W0RLI T 0000 0600 T 1000 1600 1 5 T 2200 2359 O TA C W6AMT-10 PF 12 SC #SFO3 R* to * SC SNTCRZ R* to * SC W0RLI R* to * PATH pathname port callsign force "pathname" is the name of this path. Any arbitrary 12 characters will do. This matches the entry in the ROUTE file. "port" is the letter of the port to use to connect to this mailbox on. If this is a DRSI card using TNC-TSR, you must also code the port on the C(onnect) statement. If this is a BPQ switch port of any type, you may have to code the port number also. Note that you can designate subports by extending this field. Example: B-1 would indicate a subport. You can then control forwarding by subport by using commands like "X PORT B-1". If you want to automatically forward by subport then code "no_out_fwd = Y" for this port in your PARMS.BB and then issue the X commands via WAKEUP.BB For forwarding to a file, use a port of "L" "callsign" is used to set certain parameters found in the USER file (like MAXPAC etc). Any call can be used here as long as the USER file contains the information. This call is also used for REVERSE FORWARDING. "FORCE" -- If the actual word FORCE appears after the callsign, connect via this path even if no messages. C(onnect) callsign This is the actual connect command to be used. For the DRSI card using TNC-TSR, don't forget to include port. Example: C 1:AA4RE Note 1: You must have a "C" statement in each PATH even if it will never be used. Note 2: If you are forwarding to a file (the port letter is "L", then the "C" statement will contain the name of the file. P(ort) cmd This is a command to be issued to this port. Can be used to change all sorts of things. Be careful to affect only this "channel". See the documentation for your TNC as to what is allowed. S(end) text Send the text of this line to the distant station. R(ecieve) pattern If the next line received from the distant station does not match this line disconnect. Full pattern matching can be used. "R* to *" is great for the NETROM response. Be careful when constructing your own pattern. It starts immediately after the "R" without an intervening blank. W(ait for) pattern If the next line received from the distant station does not match this line then ignoreit. Full pattern matching can be used. "R* to *" is great for the NETROM response. Be careful when constructing your own pattern. It starts immediately after the "R" without an intervening blank. Warning!! The only exit from this other than a successful match is the port timeout value. O(Order) order_info This controls how messages are ordered before forwarding. order_info can have up to three characters: A -- Order by age with oldest first T -- Order by type. T before P before B. This is actually an alphabetical sort. Special case of "P" with distribution list is same as "B" S -- Order by size. Smallest first D -- Order by day. Similar to A but only the day matters and not the time. Oldest first. R -- Reverse of D. Latest is first. If you code the letters TA then the messages will be sent by type then age within type. Thus the first message sent will be the oldest "T" message. The order will look like this: oldest "T" message . newest "T" message oldest "P" message . newest "P" message oldest "B" message . newest "B" message Note that using "A" as a parameter except as the last letter is kinda useless. If you gave "AT" then messages would be ordered by AGE then type. The probability of two messages being the same AGE (down to the second) is very very small. This is why the "D" is given. "DT" would order by DAY and then TYPE within DAY. Note 1: The "O" statement must be before any "C" statements Note 2: There is a DEFAULT_FORWARD_ORDER parameter that applies on a port basis in PARMS.BB Note 3: Any "O" statement will wipe out the ORDER parm on the "T" statement T(ime) start_time end_time start_day_of_week end_day_of_week ...options... Use this path during certain times. start_time = start time we can use path. HHMM format stop_time = stop time we can use path. If not given then we can forward anytime after start time. start_day_of_week = Day of week we can use this path. Sunday = 0, Monday = 1, etc. If omitted, can use any day. If no end_day_of_week given then path can be used this day ONLY. end_day_of_week = Last day path can be used. options = options for more control. HOUR x/y If the hour divided by x has a remainder of y then forward. Examples: HOUR 2/0 Only even hours HOUR 2/1 Only odd hours HOUR 3/1 Every 3 hrs (0100 is ok) ORDER ccc Same as "O" but only for this time period. Must be last thing on line. SIZE nnn Max size to forward in this time period TYPE aaa Type of message to forward. Use an underscore '_' for blank types. Wildcards not allowed. Max ten types. REVERSE Apply this statement only when reverse forwarding NOREVERSE Apply this statement only when not reverse forwarding FORCE Apply this statement only when force forwarding NOFORCE Apply this statement only when not force forwarding RPROMPT Send the reverse forward prompt F> NORPROMPT Do not send the reverse forward prompt F> Note 1: All start/end are INCLUSIVE. Note 2: You can have many "T" statements. If ANY of them is true, you can forward. Note 3: The "T" statement must be right after the PATH statement Note 4: The end day-of-week must be greater than or equal to the start day-of-week. The format 6 0 will not execute on Saturday and Sunday but will simply be ignored. To accomplish something like this you will need two "T" statements: One for Saturday and one for Sunday Note 5: The ORDER, SIZE, TYPE, etc operands from the FIRST "T" statement that is found to be true will be used. Note 6: If REVERSE and NOREVERSE are both specified then the "T" statement will always be ignored Note 7: If FORCE and NOFORCE are both specified then the "T" statement will always be ignored Note 8: The parameters FORCE/NOFORCE/REVERSE/NOREVERSE/HOUR should appear BEFORE the SIZE/TYPE/ORDER parameters. Examples T 0900 2300 Use this path from 0900 to 2300 T 0000 2359 1 5 Use this path from Mon to Fri T 0000 2359 0 6 HOUR 2/0 Any day but only even hours T 0000 0800 6 6 HOUR 2/1 Odd hours between midnight and eight AM on Saturday only T 1200 2359 0 6 ORDER DT Forward between noon and midnight on any day with order sequence DT T 1200 2200 0 6 SIZE 100 Forward between noon and 10 PM on any day but only messages of 100 bytes or less T 1200 2359 0 6 ORDER DT SIZE 100 Forward between noon and midnight on any day with order sequence DT but only messages of 100 bytes or less T 0000 2359 0 6 TYPE PT Forward anytime and anyday but only message types "P" and "T' T 0000 0000 0 6 NOREVERSE Never forward down this path except for reverse forward * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * Some notes on proper coding of the "T" command. Prior to V2.12, the "T" command only applied to direct forward out. It was ignored on reverse and force forwards. On newer releases, this is not true. The "T" command now applies to all forwards. This allows you to fine tune the messages to be forwarded under all conditions. Several examples follow: 1) You only want to reverse or force forward to the station: T 0000 2359 0 6 REVERSE <- This handles reverse T 0000 2359 0 6 FORCE <- This handles force Since there is no "T" line for normal forwarding, it is skipped. 2) You only want to forward private mail during the day but want to force forward anything. T 0800 1900 0 6 TYPE PT NOFORCE <- P or T mail during the day T 0000 2359 0 6 <- Everything else This coding exploits the fact that the first "T" command that is true is used. The other "T" commands are ignored * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * To ensure proper operation, execute the GF command after updating ROUTE.BB Warning!!! If forwarding is in progress when you issue the GF command then you will start to receive "routes in use" messages. This means that the data from the old ROUTE.BB file is still being used by someone connected to the BBS. The condition should clear up when those stations disconnect. * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * You can forward to a file by setting the port letter to "L" and the name of the file on the "C" statement. Example: PATH PACSAT L PACSAT C D:\PACSATS\FILE.OUT Note that the call given as the 4th word on the path line MUST be in the user file as a BBS. * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * Forwarding thru NETROM, TheNet, G8BPQ switch -------------------------------------------- Use the following snippets for NETROM forwarding C NODE1 <---Local Node SC NODE2 <---Distant Node R* to * <--- to MUST be in lower case! SC Z6ZZZ <---The other BBS R* to * Repeat the 2nd and 3rd lines as necessary for all the nodes needed * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * Forwarding thru ROSE -------------------- SC KD5SL V W5JJW-2,504926 <--- ROSE Connect Command R* to * <---} R* being * <---} Three Lines for ROSE Response R* Complete * <---} * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * NETROM/ROSE/NETROM ------------------ CO MSVKS R* to * SC N5HOF-2 V AE5V-3,318323 R* to * R* being * R* Complete * SC N5HOF R* to * * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * Using the G8BPQ switch ---------------------- If you are using the G8BPQ switch, you will always connect to the switch first. C SW SC X6XXX R* to * * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * = * Simple Example -------------- A simple BBS might have the following ACTION.BB: DISTRIBUTE DISTLIST B DISTLIST.DIS GILROY WB6ZVW KE6BX MERCED K6RAU N6OA ROUTE.BB GILROY WB6ZVW MERCED K6RAU PATH.BB PATH WB6ZVW A WB6ZVW C WB6ZVW PATH K6RAU A K6RAU C K6RAU Now the explanation. 1) The ACTION.BB says to distribute all bulletins via DISTLIST.DIS 2) DISTLIST.DIS says to send the bulletins to two destinations, MERCED and GILROY (I like to use town names). On the Gilroy line, the calls WB6ZVW and KE6BX mean that if a bulletin has already gone thru either of these stations, do not send it to "GILROY" 3) The ROUTE.BB says to send things for GILROY to WB6ZVW and for MERCED to K6RAU. The use of town names for bulletins allows them to be routed in ROUTE.BB differently than private mail.